This scenario demonstrates how to queue more than one notification and control which notifications are replaced as new notifications arrive.


Notification Queue

If this setting is enabled, Windows will queue up to five notifications and automatically cycle the tile content between them. Notifications will be saved in a FIFO (first in, first out) queue according to arrival time. The display order and animation time for notifications cannot be controlled by applications. If a new notification is received, it will always be the first to display when the tile next animates.
If the user is offline, up to five push notifications will be saved and delivered when the user comes online. These undelivered notifications also conform to the FIFO queue described above and tag logic described below.

Enable/Disable needs to be called only once in the lifetime of your app:



Enable/Disable by tile size:

Instead of a single call for all tile sizes, you can also selectively enable/disable notifications queue per tile size.

Enable/Disable for Square150x150 tile size only:



Enable/Disable for Wide310x150 tile size only:



Enable/Disable for Square310x310 tile size only:




Tags

Tags (application specified strings) can be used to replace notifications. If the notification queue is enabled, untagged notifications will queue in FIFO order. A tagged notification will replace a queued notification with the same tag. There can only be one notification with the same tag in the queue at a time. Tags which are sent from the cloud are limited to the alpha-numeric character set.

Send a Tag:

Maximum of 16 characters, the default value is 'TestTag01'.

Enter the text to be sent to the tile: